linker-messages is warn-by-default again#153968
linker-messages is warn-by-default again#153968jyn514 wants to merge 5 commits intorust-lang:mainfrom
Conversation
|
@bors try job=dist-x86_64-llvm-mingw |
|
@jyn514: 🔑 Insufficient privileges: not in try users |
4bab2bf to
51b5bec
Compare
|
@bors delegate=try |
|
✌️ @jyn514, you can now perform try builds on this pull request! You can now post |
|
@bors try job=dist-x86_64-llvm-mingw |
This comment has been minimized.
This comment has been minimized.
[wip] linker-messages is warn-by-default again try-job: dist-x86_64-llvm-mingw
|
awesome, let's try all the targets now. @bors try |
This comment has been minimized.
This comment has been minimized.
[wip] linker-messages is warn-by-default again
|
oh i forgot that try doesn't actually run all tests in this repo oops |
51b5bec to
c2e1fa8
Compare
|
r? @mati865 |
|
Some changes occurred in src/tools/compiletest cc @jieyouxu |
|
r? @fmease rustbot has assigned @fmease. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
b1f00c4 to
809ff51
Compare
|
|
|
i think https://rustc-dev-guide.rust-lang.org/tests/directives.html#controlling-when-tests-are-run already covers this. |
9efbd1f to
248a6b9
Compare
This comment has been minimized.
This comment has been minimized.
otherwise, it will get trimmed if the linker is recognized (and `for_each` is invoked), but not otherwise.
5338073 to
03f5b9a
Compare
|
@bors r+ Thanks, given the silence in Zulip thread I consider the discussion resolved. |
linker-messages is warn-by-default again cc #136096 I ended up keeping it a lint and adding an option for lints to ignore `-Dwarnings` (there was already a lint that did that actually, it was just hard-coded in rustc_middle instead of in rustc_lint_defs like I'd expect). This allows people to actually see the warnings without them failing the build in CI.
This comment has been minimized.
This comment has been minimized.
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test for acc31d4 failed: CI. Failed job:
|
|
I downgraded it for -Dwarnings but not for Cargo's I kinda wish Probably the right fix here is to teach Cargo about "capped level" warnings? Right now cargo is telling rustc the right lint level, and here we want it to be the other way around, we want something that tells cargo that I'll chat with the cargo team and see what we can agree on. |
|
Oh bummer. I can see how that flag is useful for build systems not relying on Cargo, so I doubt we'd be able to function without it. @rustbot author |
cc #136096
I ended up keeping it a lint and adding an option for lints to ignore
-Dwarnings(there was already a lint that did that actually, it was just hard-coded in rustc_middle instead of in rustc_lint_defs like I'd expect). This allows people to actually see the warnings without them failing the build in CI.View all comments